OpenEdge Data Management:<br />DataServer for Microsoft SQL Server Preface

This manual explains how to use the OpenEdge® DataServer for Microsoft SQL Server. It provides startup instructions and a brief tutorial that introduces the utilities that support the DataServer. Additionally, it discusses database design and programming issues to consider when creating applications that access the OpenEdge and SQL Server database management systems, and provides tuning and troubleshooting information.

Audience

This book is intended for programmers who want to develop OpenEdge applications that run with SQL Server databases. It assumes a fundamental knowledge of OpenEdge and SQL Server.

Organization

Describes the DataServer architecture (components and configurations) and software requirements, and provides guidelines for using the DataServer.

Discusses the differences between the OpenEdge database and MS SQL Server and the DataServer strategies for resolving these differences. Includes database design issues and application issues.

Defines relational database management system (RDBMS) stored procedures and describes how to create and implement them in an OpenEdge environment. It discusses various techniques to execute RDBMS stored procedures and Send SQL statements on the MS SQL server and load results sets directly into temp-tables. ProDataSet functionality, available through the use of temp-tables, is also briefly discussed.

Presents various dataserver performance enhancement techniques you can use, including connection pooling.

Presents instructions for configuring the DataServer and for creating, maintaining, and deploying a schema holder.

Presents various methods for starting and connecting the DataServer and describes connecting a schema holder. In addition, it provides connection guidelines and lists connection failures and OpenEdge responses.

Provides an overview of the demonstration databases and the opportunity to work with the DataServer utilities for maintaining a schema holder. In addition, it describes the Progress-to-MSS migration utility.

Describes common problems and how to work around them, including tuning your environment and resolving ODBC driver problems.

Provides information on how to migrate from the DataServer for ODBC to the DataServer for MS SQL Server, and information on issues migrating from the Version 9.1 DataServer for MS SQL Server.

Describes the utilities you use to configure, manage, start, and stop the DataServer host and client.

Typographical conventions


Convention	Description
Bold	Bold typeface indicates commands or characters the user types, provides emphasis, or the names of user interface elements.
Italic	Italic typeface indicates the title of a document, or signifies new terms.
SMALL, BOLD CAPITAL LETTERS	Small, bold capital letters indicate OpenEdge® key functions and generic keyboard keys; for example, GET and CTRL.
KEY1+KEY2	A plus sign between key names indicates a simultaneous key sequence: you press and hold down the first key while pressing the second key. For example, CTRL+X.
KEY1 KEY2	A space between key names indicates a sequential key sequence: you press and release the first key, then press another key. For example, ESCAPE H.
Syntax:
`Fixed width`	A fixed-width font is used in syntax statements, code examples, system output, and filenames.
`Fixed-width italics`	Fixed-width italics indicate variables in syntax statements.
`Fixed-width bold`	Fixed-width bold indicates variables with special emphasis.
UPPERCASE fixed width	Uppercase words are Progress® 4GL language keywords. Although these are always shown in uppercase, you can type them in either uppercase or lowercase in a procedure.
	This icon (three arrows) introduces a multi-step procedure.
	This icon (one arrow) introduces a single-step procedure.
Period (.) or colon (:)	All statements except `DO`, `FOR`, `FUNCTION`, `PROCEDURE`, and `REPEAT` end with a period. `DO`, `FOR`, `FUNCTION`, `PROCEDURE`, and `REPEAT` statements can end with either a period or a colon.
[ ]	Large brackets indicate the items within them are optional.
[ ]	Small brackets are part of the Progress 4GL language.
{ }	Large braces indicate the items within them are required. They are used to simplify complex syntax diagrams.
{ }	Small braces are part of the Progress 4GL language. For example, a called external procedure must use braces when referencing arguments passed by a calling procedure.
\|	A vertical bar indicates a choice.
...	Ellipses indicate repetition: you can choose one or more of the preceding items.

Examples of syntax descriptions

In this example, ACCUM is a keyword, and aggregate and expression are variables:

Syntax
ACCUM `aggregate expression`

FOR is one of the statements that can end with either a period or a colon, as in this example:

FOR EACH Customer: DISPLAY Name. END.

In this example, STREAM stream, UNLESS-HIDDEN, and NO-ERROR are optional:

In this example, the outer (small) brackets are part of the language, and the inner (large) brackets denote an optional item:

A called external procedure must use braces when referencing compile-time arguments passed by a calling procedure, as shown in this example:

Syntax
DISPLAY [ STREAM `stream` ] [ UNLESS-HIDDEN ] [ NO-ERROR ]

Syntax
INITIAL [ `constant` [ , `constant` ] ]

Syntax
{ `&argument-name` }

In this example, EACH, FIRST, and LAST are optional, but you can choose only one of them:

In this example, you must include two expressions, and optionally you can include more. Multiple expressions are separated by commas:

Syntax
PRESELECT [ EACH \| FIRST \| LAST ] `record-phrase`

Syntax
MAXIMUM ( `expression` , `expression` [ , `expression` ] ... )

In this example, you must specify MESSAGE and at least one expression or SKIP [ (n) ], and any number of additional expression or SKIP [ ( n ) ] is allowed:

Syntax
MESSAGE { `expression` \| SKIP [ ( `n` ) ] } ...

In this example, you must specify {include-file, then optionally any number of argument or &argument-name = "argument-value", and then terminate with }:

Long syntax descriptions split across lines

Some syntax descriptions are too long to fit on one line. When syntax descriptions are split across multiple lines, groups of optional and groups of required items are kept together in the required order.

Complex syntax descriptions with both required and optional elements

Some syntax descriptions are too complex to distinguish required and optional elements by bracketing only the optional elements. For such syntax, the descriptions include both braces (for required elements) and brackets (for optional elements).

Syntax
{ `include-file` [ `argument` \| `&argument-name = "argument-value"` ] ... }

Syntax
WITH [ ACCUM `max-length` ] [ `expression` DOWN ] [ CENTERED ] [ `n` COLUMNS ] [ SIDE-LABELS ] [ STREAM-IO ]

In this example, ASSIGN requires either one or more field entries or one record. Options available with field or record are grouped with braces and brackets:

Syntax
ASSIGN { [ FRAME `frame` ] { `field` [ = `expression` ] } [ WHEN `expression` ] } ... \| { `record` [ EXCEPT `field` ... ] }

OpenEdge messages

OpenEdge displays several types of messages to inform you of routine and unusual occurrences:

OpenEdge messages end with a message number in parentheses. In this example, the message number is 200:

If you encounter an error that terminates OpenEdge, note the message number before restarting.

Obtaining more information about OpenEdge messages

In Windows platforms, use OpenEdge online help to obtain more information about OpenEdge messages. Many OpenEdge tools include the following help menu options to provide information about messages:

Preface

Purpose